Reviewable status: 0 of 7 files reviewed, 3 unresolved discussions

options.go line 1312 at r1 (raw file):

// KVs, overriding global policies. Values can be configured to be stored in-place,
// in value blocks, or in blob files.
type ValueStoragePolicyAdjustment struct {

I think we can simplify this to just a set of fields.

type ValueStoragePolicyAdjustment struct {
   DisableBlobSeparation bool
   OverrideBlobSeparationMinimumSize int
   DisableSeparationBySuffix bool
}

Zero value means no adjustment.

options.go line 1320 at r1 (raw file):

	// keys (where the smallest suffix is the latest version), but should be
	// disabled for keys where the suffix does not correspond to a version.
	DisableSeparationBySuffix bool

It would be good to document the of cases of where values can go, with or without this flag, for the three possibilities:

• most recent suffix with value >= MinimumSize
• older suffix with value >= MinimumSize
• older suffix with value < MinimumSize

compaction.go line 3491 at r1 (raw file):

			// aggressive value separation policy for this output.
			vSep.SetNextOutputConfig(valsep.ValueSeparationOutputConfig{
				MinimumSize:                    spanPolicy.ValueStoragePolicy.MinimumSize,

[nit] maybe we should rename MinimumSizeForBlob or similar

Reviewable status: 0 of 8 files reviewed, 1 unresolved discussion (waiting on @RaduBerinde)

options.go line 1312 at r1 (raw file):

Done.

options.go line 1320 at r1 (raw file):

Done.

Reviewable status: 0 of 8 files reviewed, 2 unresolved discussions (waiting on @xinhaoz)

options.go line 1330 at r2 (raw file):

	// - If blob separation is disabled, the value will be written to a value
	// block within the sstable.
	// - Otherwise, the KV will be subject to regular value separation rules.

[nit] There is no "otherwise" (separation is either enabled or disabled)